Updated as suggested. The rule is now in src/alterschema/common/ with mutates = std::true_type and a transform that sets the schema to false. It is registered under both the linter and canonicalizer bundles, and canonicalizer tests have been added for all four dialects alongside the existing lint tests.

Thanks for the detailed feedback. I have updated the implementation to address all your points:

Rule changes (src/alterschema/common/incoherent_exclusive_limits.h):

• Anchor Guards: Added $anchor and $dynamicAnchor checks to the rule's condition() to prevent mutating schemas that define reference targets.
• Non-Destructive Transform: Instead of unconditionally converting the schema to false, the transform now introduces not: {} (which canonicalizes to not: true). If not already exists, it wraps both inside a new allOf. If allOf already exists, it directly appends {not: {}} to the array in-place to avoid any copy-assignment overhead.

Test coverage:

• Draft 2019-09 & Draft 2020-12: Added test cases covering $ref integrity preservation as well as explicit tests for $anchor and $dynamicAnchor guards (validating that the schema remains unmutated when these are present).
• Draft 6 & Draft 7: Anchor-related tests are omitted since $anchor and $dynamicAnchor do not exist in these older dialects. Furthermore, since $ref in Draft 6/7 has exclusive sibling-swallowing behavior under validation anyway, the integration tests successfully verify that reference targets are safely reframed and canonicalized.

All 39 unit tests are passing cleanly and the full alterschema test suite has been verified.

Thanks for the follow-up feedback ,You are completely correct, and I have simplified the implementation to address all concerns:

1. Vocabulary Safety & Condition Simplification:
   Removed the not and allOf checks from the condition() method entirely. I had originally added them as an early-termination optimization to check if a schema was already marked as unsatisfiable by a previous transform. However, as you noted, since the transform() method already erases the exclusiveMinimum and exclusiveMaximum keywords, the rule naturally will never apply more than once anyway. Removing these checks completely resolves the vocabulary restriction issue (where these applicator keywords require the Applicator vocabulary to be active in Draft 2019-09 and Draft 2020-12).

2. Anchor Guard Removal:
   Removed the $anchor and $dynamicAnchor guards. These were originally introduced back when we were unconditionally converting the entire schema to false (which would have wiped out the anchors). Now that the transform is non-destructive and only appends the validation constraint structurally (either as not: {} or wrapped under allOf), all $anchor, $dynamicAnchor, $defs, and sibling keywords remain perfectly intact at their original location without breaking any references.

I also cleaned up the test suites by removing the redundant anchor-related tests since the rules are now simpler and rely on standard framework-level anchor preservation. All 36 integration and linter tests are passing successfully.